• route write_data through cross-db write methods whenever database is not None
• preserve explicit empty/invalid database strings so the engine can validate them

We need this because None is the sentinel for “use the trigger DB.” Any explicit string value, including an empty or invalid database name, should take the cross-db path so the engine can validate it and return the correct error instead of silently writing to the trigger DB.